Classifying Traditional Licensing API

The Sentinel RMS licensing library is used to integrate the API calls to your client application. There are different integration styles that offer varying degrees of functionality.

1.The Quick-API is typically meant for quick licensing using just two API functions—especially for applications that require only one license for each instance of the program.

It is the simplest of the three API sets (the other two are described below) and requires only the addition of two function calls. The first initializes contact with the License Manager and automatically updates the license. This call is made during program initialization. The other is made at the end of the program to return the license and disable licensing.

2.The Standard-API offers a full spectrum of licensing models including the licensing of multiple features in a single application. It requires adding only four to five function calls. The program begins by initializing the client library and requesting a license. At the end of the program, calls are made to release the license and clean up the client library. This method provides greater control and flexibility to the developer.

3.The Advanced-API provides rich-set of API functions for performing advance licensing operations.

The additional functions that augment the Standard-API to form the Advanced-API can be grouped into one of several categories as follows:

1.Client Configuration functions, which allow an application to retrieve or change default values for such settings as port number, License Manager name, broadcast interval, timeout interval, etc.

2.Client Query functions, which provide a snapshot of the current status of the License Manager and the features it licenses.

3.Feature Query functions, which retrieve feature licensing information from the license manager such as name and version.

4.Client Utility functions, which provide client library capabilities such as the hostname of the machine running the Sentinel RMS protected application, the names of the computers running the License Manager, and other facilities useful to certain specialized applications.

5.Error handling functions, which make possible turning error handling on and off, registering custom error handlers, and printing error messages.

For details on thee above, refer to Traditional API: On-premises Deployment Mode of the Sentinel RMS SDK API Reference Guide.